Method for organizing large numbers of documents

ABSTRACT

A computer product including a data structure for organizing of a plurality of documents, and capable of being utilized by a processor for manipulating data of the data structure and capable of displaying selected data on a display unit. The data structure includes a plurality of directionally interlinked nodes, each node being associated with one or more documents having a header and body text. All the documents are associated with a given node and have identical normalized body text. All documents that have identical normalized body text are associated with the same node. One or more of the nodes is associated with more than one document. For any node that is a descendent of another node, the normalized body text of each document associated with the node is inclusive of the normalized body text of a document that is associated with the other node.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a Division of application Ser. No. 11/968,433 filed Jan. 2, 2008 and claims the benefit of U.S. Provisional Application No. 60/974,974 filed on Sep. 25, 2007 and U.S. Provisional Application No. 60/947,606 filed on Jul. 2, 2007. The disclosure of the prior applications is hereby incorporated by reference herein in its entirety.

FIELD OF THE INVENTION

The present invention relates to the field of organizing large numbers of documents.

BACKGROUND OF THE INVENTION

In litigation proceedings, as well as for other functions, often massive amounts of documents must be reviewed. Certain organizational methods for arranging documents exist in the art. Emails are a particular type of document that are useful to review in structures, to help make sense of the proceedings and reduce the number of documents that need to be read.

The need to detect near duplicate documents arises in many applications. Typically this may occur in litigation proceedings. In litigation, often one of the parties initiates discovery proceedings which force the rival party to reveal all the documents at his disposal that pertain to the legal dispute. In order to meet the provisions of the discovery procedure, the disclosing party hands piles of documents, sometimes in order to duly meet the full disclosure stipulations, or in certain other cases, as a tactical measure to flood the other party with huge amounts of documents, thereby incurring the receiving party considerable legal expenses in the tedious task of determining which documents are relevant to the dispute under consideration. In many cases, out of the repertoire of disclosed documents, many are similar to each other. A preliminary knowledge which will group and/or flag documents that are similar to one another would streamline the screening process, since for example, if a certain document is classified as irrelevant, then probably all the documents that are similar thereto, are also deemed irrelevant. There are numerous other applications for determining near duplicate documents, sometimes from among a very large archive of documents (possibly of the order of millions of documents or more).

A common type of document that is examined in litigation procedures is emails. If collected from user accounts of various users in a company, there is likely to be a degree of duplicity between users. Duplicity may occur because the same email is sent to a number of recipients at once, or for other reasons. Also, many times, emails are near duplicates of one another.

LIST OF RELATED ART

U.S. Pat. No. 7,035,876 to Kawai et al provides a system and method for evaluating a structured message store for message redundancy. A header and a message body are extracted from each of a plurality of messages maintained in a structured message store. A substantially unique hash code is calculated over at least part of the header and over the message body of each message. The messages are grouped by the hash codes. One such message is identified as a unique message within each group. In a further embodiment, the messages are grouped by conversation thread. The message body for each message within each conversation thread group is compared. At least one such message within each conversation thread group is identified as a unique message. The invention requires that all emails in a set have the same subject line. Additionally, all emails must have the same attachment to be considered part of the same set.

U.S. Pat. No. 6,119,124: Method for clustering closely resembling data objects. A computer-implemented method determines the resemblance of data objects such as Web pages. Each data object is partitioned into a sequence of tokens. The tokens are grouped into overlapping sets of the tokens to form shingles. Each shingle is represented by a unique identification element encoded as a fingerprint. A minimum element from each of the images of the set of fingerprints associated with a document under each of a plurality of pseudo random permutations of the set of all fingerprints, are selected to generate a sketch of each data object. The sketches characterize the resemblance of the data objects. The sketches can be further partitioned into a plurality of groups. Each group is fingerprinted to form a feature. Data objects that share more than a certain numbers of features are estimated to be nearly identical.

U.S. Pat. No. 6,189,002: Process and system for retrieval of documents using context-relevant semantic profiles. A process and system for database storage and retrieval are described along with methods for obtaining semantic profiles from a training text corpus, i.e., text of known relevance, a method for using the training to guide context-relevant document retrieval, and a method for limiting the range of documents that need to be searched after a query. A neural network is used to extract semantic profiles from text corpus. A new set of documents, such as World Wide Web pages obtained from the Internet, is then submitted for processing to the same neural network, which computes a semantic profile representation for these pages using the semantic relations learned from profiling the training documents. These semantic profiles are then organized into clusters in order to minimize the time required to answer a query. When a user queries the database, i.e., the set of documents, his or her query is similarly transformed into a semantic profile and compared with the semantic profiles of each cluster of documents. The query profile is then compared with each of the documents in that cluster. Documents with the closest weighted match to the query are returned as search results.

U.S. Pat. No. 6,230,155: Method for determining the resemblance of documents. Disclosed is a method for facilitating the comparison of two computerized documents. The method includes loading a first document into a random access memory (RAM), loading a second document into the RAM, reducing the first document into a first sequence of tokens, reducing the second document into a second sequence of tokens, converting the first set of tokens to a first (multi)set of shingles, converting the second set of tokens to a second (multi)set of shingles, determining a first sketch of the first (multi)set of shingles, determining a second sketch of the second (multi)set of shingles, and comparing the first sketch and the second sketch. The sketches have a fixed size, independent of the size of the documents. The resemblance of two documents is provided, using a sketch of each document. The sketches may be computed fairly fast and given two sketches, the resemblance of the corresponding documents can be computed in linear time in the size of the sketches.

U.S. Pat. No. 6,240,409: Method and apparatus for detecting and summarizing document similarity within large document sets. A method and apparatus are disclosed for comparing an input or query file to a set of files to detect similarities and formatting the output comparison data are described. An input query file that can be segmented into multiple query file substrings is received. A query file substring is selected and used to search a storage area containing multiple ordered file substrings that were taken from previously analyzed files. If the selected query file substring matches any of the multiple ordered file substrings, match data relating to the match between the selected query file substring and the matching ordered file substring is stored in a temporary file. The matching ordered file substring and another ordered file substring are joined if the matching ordered file substring and the second ordered file substring are in a particular sequence and if the selected query file substring and a second query file substring are in the same particular sequence. If the matching ordered file substring and the second query file substring match, a coalesced matching ordered substring and a coalesced query file substring are formed that can be used to format output comparison data.

U.S. Pat. No. 6,349,296: Method for clustering closely resembling data objects. A computer-implemented method determines the resemblance of data objects such as Web pages. Each data object is partitioned into a sequence of tokens. The tokens are grouped into overlapping sets of the tokens to form shingles. Each shingle is represented by a unique identification element encoded as a fingerprint. A minimum element from each of the images of the set of fingerprints associated with a document under each of a plurality of pseudo random permutations of the set of all fingerprints, are selected to generate a sketch of each data object. The sketches characterize the resemblance of the data objects. The sketches can be further partitioned into a plurality of groups. Each group is fingerprinted to form a feature. Data objects that share more than a certain numbers of features are estimated to be nearly identical.

U.S. Pat. No. 6,658,423: Detecting duplicate and near-duplicate files. Disclosed is an improved duplicate and near-duplicate detection. Techniques may assign a number of fingerprints to a given document by (i) extracting parts from the document, (ii) assigning the extracted parts to one or more of a predetermined number of lists, and (iii) generating a fingerprint from each of the populated lists. Two documents may be considered to be near-duplicates if any one of their respective fingerprints match.

U.S. Pat. No. 6,654,739: Lightweight document clustering is a procedure for clustering documents that operates in high dimensions, processes tens of thousands of documents and groups them into several thousand clusters or, by varying a single parameter, into a few dozen clusters. The procedure is specified in two parts: computing a similarity score representing the k most similar documents (typically the top ten) for each document in the collection, and grouping the documents into clusters using the similar scores.

U.S. Pat. No. 6,751,628: Process and system for sparse vector and matrix representation of document indexing and retrieval. Disclosed is a new data structure and algorithms which offer at least equal performance in common sparse matrix tasks, and improved performance in many. This is applied to a word-document index to produce fast build and query times for document retrieval.

U.S. Pat. No. 7,139,756: System and method for detecting duplicate and similar documents. A system and a method are described for rapidly determining document similarity among a set of documents, such as a set of documents obtained from an information retrieval (IR) system. A ranked list of the most important terms in each document is obtained using a phrase recognizer system. The list is stored in a database and is used to compute document similarity with a simple database query. If the number of terms found to not be contained in both documents is less than some predetermined threshold compared to the total number of terms in the document, these documents are determined to be very similar. It is shown that these techniques may be employed to accurately recognize that documents, that have been revised to contain parts of other documents, are still closely related to the original document. These teachings further provide for the computation of a document signature that can then be used to make a rapid comparison between documents that are likely to be identical.

Abdur Chowdhury Duplicate Data Detection The algorithm is based on IDF of the tokens. The algorithm steps are: 1. Get document. 2. Parse document into a token steam, removing format tags. 3. Using term thresholds (idf), retain only significant tokens. 4. Insert relevant tokens into Unicode ascending ordered tree of unique tokens. 5. Loop through token tree and add each unique token to the SHA1 (1995) digest. Upon completion of token tree loop, a (doc_id, SHA1 Digest) tuple is defined. 6. The tuple (doc_id, SHA1 Digest) is inserted into the storage data structure based on SHA1 Digest key. 7. If there is a collision of digest values, then the documents are similar. Conrad et. Al: In a series of a few papers, they describe a method that is based on the IDF measure of tokens, and the size of the documents. They are also provided a method of selecting the corpus to evaluate the IDF of a token. There is thus a need in the art to provide for a new system and method for determining near duplicate objects. There is still further need in the art to provide for a new system and method for determining near duplicate documents.

SUMMARY OF THE INVENTION

The present invention relates to the organization and display of data, particularly when the source of the data is a huge number of documents.

According to an aspect of the invention, there is provided a computer product including a data structure for organizing of a plurality of documents, and capable of being utilized by a processor for manipulating data of the data structure and capable of displaying selected data on a display unit. The data structure comprises:

a) a plurality of directionally interlinked nodes, each node being associated with at least one document having at least a header and body text; and wherein all documents associated with a given node having substantially identical normalized body text, and wherein all documents having substantially identical normalized body text being associated with the same node, and wherein at least one node being associated with more than one document; b) for any first node of the nodes that is a descendent of a second node of the nodes, the normalized body text of each document associated with the first node is substantially inclusive of the normalized body text of each document that is associated with the second node.

According to a further embodiment of the invention, all documents associated with a given node further have substantially identical normalized subject parameter in the header.

According to a further embodiment of the invention, there is provided that the body text of each document associated with said first node is substantially inclusive of the body text of each document that is associated with said second node, irrespective of whether a normalized subject parameter from a header of a document associated with said first node and a normalized subject parameter from a header of a document associated with said second nodes are identical.

According to another aspect of the invention, there is provided a method for organizing documents into nodes, in which a node represents a group of substantially equivalent documents. The method comprises:

(i) providing a plurality of original documents, each comprising a header and a body, and wherein the header comprises at least one parameter and wherein the body comprises text,

(ii) selecting a document from among the documents and associating the document with a node, comparing at least a portion of the body text of the document to at least a portion of the body texts of other documents from amongst the plurality of documents, and in the case of a match, merging the node associated with the document with a node associated with the matching document, (iii) searching the body of the document to locate a first instance of header-type text, wherein the header-type text contains at least one header parameter; (iv) constructing a presumed document comprising a header and a body, wherein the header of the presumed document comprises one or more parameters from the header-type text located within the body of the original document, and wherein the body of the presumed document substantially comprises the text located after the header-type text in the body of the original document, and associating the presumed document with a node; (v) comparing at least a portion of the body text of the presumed document to at least a portion of the body texts of at least one other documents from among the plurality of documents and in the case of a match, merging a node associated with the presumed document with a node associated with the matching document, (vi) if the comparison of (v) does not find a match, processing repeatedly the remainder of the body of the document for successive instances of header-type text, as stipulated in stages (iii)-(v), and for each instance, constructing a presumed document, comparing for any matching documents to the presumed document, and if found, merging the nodes associated with the matching documents, until no new presumed documents are found.

According to another aspect of the invention, a method is provided for reducing duplicate document display of a large number of documents, in which the method involves:

a) comparing a fingerprint of a document with previously stored document fingerprints, wherein a fingerprint is formed for each of at least a portion of the normalized body text and a normalized subject parameter of a document, wherein the comparison for detecting and indicating duplicating documents; b) searching the document for instances of header-type text, searching in text order through the normalized body text of the document, and if header-type text is found in the search,

-   -   i) deriving a presumed document comprising a header and a body         text, by treating parameters from the instance of header-type         text in the document as parameters of a header for the presumed         document, and by treating all ensuing body text as the body text         of the presumed document, and applying step a) to the presumed         documents, and     -   ii) if the fingerprint of the presumed document is unique,         continuing to search the normalized body text of the document         from which the presumed document is derived for further         instances of header-type text, searching in text order through         the normalized body text of the document, and if a further         instance of header-type text is found in the search, applying         step i) to derive and process an additional presumed document,         and     -   iii) repeating step ii) until no more instances of header-type         text are found.

In an embodiment of the invention, the method described above also involves providing a plurality of nodes, and associating each document having a unique fingerprint with a unique node, and associating each document detected as duplicating to a prior document with the node associated with the prior document.

In an embodiment of the invention, the method described above also involves linking nodes to provide that a node associated with a first presumed document becomes the parent of the node associated with the document from which the first presumed document is derived, and to provide that the node associated with each sequentially derived presumed document derived from the same document becomes a parent of the node associated with the previously derived presumed document.

In an embodiment of the invention, the method described above also involves displaying the nodes in a computer format, and affiliating each node with the body text and subject parameter of the document associated with the node.

According to another aspect of the invention, there is provided a computer product including a data structure for organizing of a plurality of documents, and capable of being utilized by a processor for manipulating data of the data structure and capable of displaying selected data on a display unit. The data structure comprises one or more trees, wherein a tree comprises at least a trunk and at least one node, each node being associated with a document having at least a header and body text, and wherein a trunk being associated with zero or more documents having at least a header and a body text and wherein all documents whose body text includes the same included document are associated with the same tree, and wherein a unique inclusive document, as well as documents that duplicate to said unique inclusive document, are associated with one of one or more unique nodes of said tree, and wherein an included document, as well as documents that duplicate to said included document, are associated with the trunk of the tree.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to understand the invention and to see how it may be carried out in practice, an example embodiment will now be described, by way of non-limiting example only, with reference to the accompanying drawings, in which:

FIGS. 1 a to 1 c illustrate an example set of three emails;

FIGS. 2 a and 2 b illustrate how an inclusive document, such as an email, may be expanded into a set of presumed documents, in accordance with an embodiment of the invention;

FIG. 3 illustrates a first generalized flow diagram of operational stages in accordance with an embodiment of the invention;

FIGS. 4 a-4 e illustrate the comparison and storage of fingerprints, in accordance with an embodiment of the invention;

FIGS. 5 a-5 c illustrate a second generalized flow diagram, with examples of operational stages in accordance with an embodiment of the invention;

FIGS. 6 a-6 c illustrate sample displays showing documents organized according to trees;

FIG. 7 illustrates a sample display of organizational trees arranged as document sets;

FIG. 8 a illustrates a prior art tree;

FIGS. 8 b-8 c illustrate two types of trees in accordance with embodiments of the invention;

FIGS. 8 d-8 e illustrate output forms in accordance with embodiments of the invention; and

FIG. 9 illustrates how the contents of two processors may be arranged together in trees, according to an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

It should be noted that the invention is described for convenience, with reference to documents. The term documents is understood to include files including text or representing text, such as Microsoft Word documents, Excel documents, mail documents, etc. References to documents embrace also derivative thereof, such as known per se canonic representation of a document. In accordance with certain embodiments, documents include at least text and/or numbers. In one embodiment, the documents are Microsoft Office® documents, such as e-mails in selected format. The format may be, for example, Microsoft Outlook, Lotus Notes, etc. The term documents is not confined to obvious documents, but applies also to other types of data objects, such as documents within a ZIP file, e-mails in MS Outlook PST file format, attachments, etc.

In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art, that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present invention.

Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions, utilizing terms such as, “processing”, “comparing”, “linking”, “connecting”, “representing”, “detecting”, “searching”, “deriving”, “calculating”, “storing”, “inserting”, “determining”, “treating”, “repeating”, “identifying”, “labeling”, “indexing”, “running an algorithm”, “to return, if positive . . . if negative . . . ”, “creating”, “showing”, “displaying”, “suppressing”, “setting levels”, “stringing nodes”, “organizing”, “associating”, “affiliating”, or the like, refer to the action and/or processes of a computer or computing system, or processor or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities within the computing system's registers and/or memories into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices.

Embodiments of the present invention may use terms such as processor, computer, apparatus, system, sub-system, module, unit and device (in single or plural form) for performing the operations herein. Devices may be specially constructed for the desired purposes, or the invention may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs) electrically programmable read-only memories (EPROMs), electrically erasable and programmable read only memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions, and capable of being coupled to a computer system bus.

The processes/devices (or counterpart terms specified above) and displays presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct a more specialized apparatus to perform the desired method. The desired structure for a variety of these systems will appear from the description below. In addition, the present invention is not limited to any particular programming language or type. It will be appreciated that a variety of programming languages may be used to implement the teachings of the inventions as described herein.

The following description seeks to explain by way of example what inclusiveness is, in relation to emails. With reference now to FIGS. 1 a-1 c, a set of three example emails are illustrated. FIG. 1 a illustrates a first email. The email includes header 11 and body text 21. Header 11 contains metadata for the document, that in this case includes To: and From: fields, a date of transmission, and a Subject: field, or “subject” parameter. Parameters from header 11 indicate that the email was sent by Andy, to Bill on Sunday. Subject parameters are often related to body text, in the present email, the subject parameter is the words “Old House”.

FIG. 1 b illustrates a second email. The email includes header 12 and body text 22. Header 12 indicates that the email has been sent as a reply to Andy, from Bill, on Monday. Body text 22 includes new text from Bill, some metadata regarding the email of FIG. 1 a, and a copy of body text 21. Each line of text, from the metadata until the end of the included body text 21, is prefaced by a “>” character.

FIG. 1 c illustrates a third email. Header 13 indicates that it has been forwarded by Andy to Charles on Tuesday, with a carbon copy sent to Bill. Body text 23 includes new text from Andy, a line stating that forwarded text is beginning, metadata regarding Bill's forwarded email, and a copy of body text 22.

As has been noted, body text 23 is inclusive of body text 22, which is inclusive of body text 21. Thus, if one wished to read the minimum number of texts, one could suffice by reading only body text 23. A meaning of the term ‘inclusive document’ in the present context is directed to one document from amongst a group of documents, in which the inclusive one includes the text (or the normalized text) of all the others.

In the set of documents of FIG. 1, FIG. 1 c would be considered the inclusive document of the three, since its body text 23 includes all the body text of the other two. Similarly, FIG. 1 b can be considered inclusive of FIG. 1 a, since body text 22 includes all the text of body text 21.

It will be noted in certain embodiments, when determining inclusiveness, that a first document is only considered inclusive of a second document if the first document contains within its body text the entire body text of the second document. However, a document can still be considered inclusive if certain minor differences are present, such as for example, normalization having been applied, or legal disclaimers at the end of an email having been stripped, or only a certain number of lines or characters of the body text are considered as significant.

Having described what inclusiveness represents, with relation to emails, the following describes arrangement of documents, such as emails, according to inclusiveness. In accordance with certain embodiments of the present invention, there is provided a method for arranging a large number of documents relative to one another. Documents can be any type of document, but a particular usage of the present invention relates to emails. Documents may be loosely described as including both “body text” and “metadata”. Body text refers to the viewable text of the document, while metadata (also referred to herein as the document “header”) includes information and fields concerning the document, for example the fields for: author, date of creation, subject, date modified, etc. With regard to emails, which are anticipated to be a particularly useful beneficiary of the present invention, a great deal of information is stored as metadata for each email, often including the above fields, and others, application specific, such as Conversation ID (in Microsoft Outlook). The header of each email displays some of the metadata for the email, for example header 11 includes From: and To: fields, as well as Date: (date sent) and Subject: fields.

Emails may very often be inclusive documents. As shown in FIG. 1, it is common for people to respond to emails by hitting the reply or forward button at the top of the email program screen. This action prepares for them a new email, with some or all header fields already filled in, and provides all the body text of the email being responded to, in the body of message. Usually this included body text is preceded by some sort of header-type text to indicate what it is. An example of header-type text is shown in FIG. 1 b, where the header-type text is:

>Date: Sun, 25 Jul. 2006 15:42:23+0300

>To: Bill@boxmail.com,

>From: Andy Anderson <Andy.anderson@013.com>

>Subject: Old House??

When a few documents from amongst a large number of documents relate to the same subject matter, it is convenient to have them grouped together. Various organizational techniques are known in the art, such as classifying documents according to metadata associated with the documents, for example according to creation date of the document, or the author's name, or the subject line. In accordance with certain embodiments of the present invention, there is provided a method for grouping documents according to included documents.

The method for grouping and arranging documents according to inclusiveness can be applied with at least two different outputs:

1) A set of directionally interlinked nodes are created, in which each node is associated with at least one document. Each document has header parameters and body text, and if more than one document exists with the substantially identical body text, all are associated with the same node. In order to determine if documents are substantially identical, normalization is applied to the text, to remove any irrelevant characters. The level of normalization is variable, and no normalization is also considered normalization, since it represents an equal output to input. Large degrees of normalization are also possible, as described below. As stated, identical documents are associated with the same node, and, in many cases, many documents will all be associated with the same node. The nodes are directionally interlinked as follows. A first node is arranged or indicated to be a descendant of a second node if the body text of each document associated with the first node is substantially inclusive of the body text of each document that is associated with the second node.

The directionally interlinked nodes can be displayed by a processor on a display unit as a representational tree of nodes. The representational tree shows graphically the relationship between the nodes, indicating the degree of inclusiveness that each document associated with the nodes has relative to the others in the tree. So, in effect, the nodes of the tree graphically display the order of the documents, starting with the shortest one and leading to the longest, most inclusive document.

2) A group of documents that all include a certain document text is created. From this group, certain inclusive documents are identified as being inclusive of the others. In accordance with certain embodiments of the method, there is an advantage in that a reviewer can read all the text content of the entire group of documents by reading only the identified documents.

These two outputs are provided for exemplary purposes only, and should by no means be considered as limiting the scope of the invention.

In both of the above cases, it is noted that inclusiveness includes inclusiveness of whole documents, wherein a whole document has a header as well as body text. However, there are at least three cases in which documents are considered inclusive even though the body text of one is not wholly inclusive of the other. Firstly, normalization may have stripped the body text of part of the text. Secondly, if a first document is inclusive of a document that is near-duplicated to a second document, the first document is considered inclusive of the second document, and the node associated with the first document is a descendant of the second document. Thirdly, it may be desired to use only a portion of the body text for the purposes of determining inclusiveness. For example, one might want to consider only the first 2000 characters of all documents. Other variants besides the specified example are also applicable.

Both of these outputs will be described in more detail with reference to FIGS. 8 b-8 c.

A variety of methods may be used in order to group and arrange documents according to inclusiveness; the present disclosure will describe example methods, from which other equivalent methods can be extrapolated.

Documents and emails often indicate that other, previous, documents once existed. An example of this in FIG. 1 b—for even without ever seeing FIG. 1 a, FIG. 1 a can be derived from FIG. 1 b. One embodiment for the present invention includes the step of deriving, or reconstituting presumed emails from other emails. As mentioned, FIG. 1 a can be derived from FIG. 1 b, while both FIG. 1 a and FIG. 1 b can be derived from FIG. 1 c. When a document such as an email is derived it is termed a “presumed document”—a document that is presumed to have existed due to its incorporation within another document. After a presumed document is created, it is then compared with other documents. If the presumed document is found to be identical with any other documents, then the document from which the presumed document is derived, and the document to which the presumed document is similar, are identified as belonging to the same group, or tree.

In one manner of implementation of the present invention, each document that is to be classified is first provided with identification. This identification is used in accordance with certain embodiments and is not required in other embodiments of the present invention; identification is a method that will be referred to later in this disclosure. The present example is used with reference to emails, but may be used with other types of documents.

A large number of emails are provided, so that they may be organized according to inclusiveness. Each email is first provided with three types of identification: an email number, (MailID), an index value (Idx), and an individual, unique document number (DocID). These may be entered into the data structure. The MailID is assigned according to the number of emails that have previously been processed, the index value is set at zero, and the DocID is identical to the MailID. The purpose of these latter two identifiers will be explained in greater detail below.

Emails, as mentioned, in many cases, are expandable into a set of presumed, or derived or secondary documents. With reference now to FIG. 2, an email is shown, in terms of general structure, and with email text content not shown, for clarity. Email text content may resemble that of FIG. 1 c, for example. The email of FIG. 2 is separately recorded as having identification details as follows: MailID is set to X, DocID is set to X, and the index is zero. The email is referred to herein as Email X₀, in which X is the MailID and ₀ represents the index value. In a real-life scenario, the letter X would preferably be replaced with a numeric identifier. Email X₀ consists of a header and a body, and these are labeled as header hX₀ and body text bX₀.

Presumed emails may be derived based on the appearance of header type text within the body text. For example, Body text bX₀ contains several instances of header-type text. Header-type text indicates that all the remaining text in the email, after the header-type text, is likely to have been originally the body text of an earlier document. Thus a presumed email can be created for each instance of header-type text. The first instance of header-type text indicates a presumed email, and this presumed email is provided with identification as follows: MailID remains X, DocID is a numeric string specific to this particular presumed email, and the index value is 1, implying that this is the first presumed email originating from the original email X₀. This first ‘presumed document’ is referred to herein as document X₁, and it consists of header hX₁ and body text bX₁. Body text bX₁ is derived from a copy of all the remaining body text following the header-type text identified as header hX₁ in document X₀.

The remaining text of body text bX₀, following the header-type text already located, can still be searched for further instances of header-type text, to create further presumed emails. A second instance of header-type text is found, to suggest a second presumed email, with identification as follows: MailID remains X, DocID is a numeric string specific to this particular presumed email, and the index is 2, implying that it is the second presumed email originating from document X₀. This second ‘presumed email is referred to herein as X₂, and includes header hX₂, composed of the header-type text that caused it. All body text that follows header hX₂, namely body text bX₂, forms the body text for presumed email X₂.

The remaining text of body text bX₀ is also expandable, and a third instance of header-type text can be located. This forms presumed email X₃, with header hX₃ formed of the header-type text that indicated the presumed email, and with body text formed of all of body text that follows header hX₃, namely body text bX₃.

With reference now to FIG. 2 b, Email Y₀ is also expandable into original document Y₀, plus two presumed emails, Y₁ and Y₂. Y₁ consists of header hY₁, and body text bY₁, while Y₂ consists of header hY₂ and body text bY₂. Headers hY₁ and hY₂ are composed of header-type text located in body text Y₀, in order of appearance respectively. Body texts bY₁ and bY₂ are composed of all of the text of body text Y₀ that followed the header-type texts of headers hY₁ and hY₂ respectively.

As has been shown, it is possible to ‘expand’ an email or other document into an email plus a set of presumed emails that were included within the body text. The set of presumed emails can then be used for comparison with other emails to determine which other emails should be considered in the same group. However, creating ‘presumed documents’ as described is only one way of implementing the present invention, and the organization of documents according to inclusiveness may be alternatively implemented in many other ways.

According to certain embodiments of the invention, documents whose contents have not been derived from within the body text of other documents of the set may be referred to herein as ‘original documents’, this term is relative to ‘presumed documents’ that have been derived from others. ‘Original documents’ however need not be true document originals, for example they may be extracted from bulk files or document copies.

Having described ‘presumed documents’ in accordance with certain embodiments, the following seeks to describe the process of preparing fingerprints (for example, CRC, implemented using MD5) of the documents. The fingerprints are prepared for the purpose of comparing original and presumed documents with other documents from the group of documents. Two documents that have the same fingerprints, have with high probability the same content.

In order to determine whether documents should belong to the same group—that one is inclusive of the other, or that two are identical to one another, a document comparison may be done. “Matching” and “equivalent” and “duplicating” are other terms that refer herein to two or more texts that are substantially identical.

According to one embodiment, a copy of each document that has been processed is stored in a repository, and as each new document is processed, it is compared with previously stored documents, before being stored itself. According to one embodiment, the repository is part of the data structure, or it may be a separate unit.

One implementation involves the following: the document in its entirety is not used for the comparison since it may be huge. Instead, only a fingerprint of the text of each document is compared. The fingerprint is created as follows. A first fingerprint, for example, a CRC (cyclic redundancy check), or for example, CRC-MD5, is compiled for the body text or the normalized body text of the document. A subject parameter is determined for the document, normalized and a second CRC is compiled for the normalized subject parameter. If the document is an email, the subject parameter may be derived from the Header parameter of the field labeled “Subject:”. For example, in FIG. 1 a, the subject parameter is the phrase: “Old House??”. Other types of documents have other types of subject parameters, for example, the subject parameter may be a subject field filled in by a user when the document is created or modified, or it may be the title or file name or path of the document. It could be that a document has no subject field, or that the subject parameter is unknown. In accordance with certain embodiments, the subject parameter is a useful field for organizing documents. In accordance with other embodiments, the subject parameter is not used, for example, the present invention allows the subject parameter to be entirely disregarded, or disregarded only if empty, or alternatively, considered blank if it is unknown.

Fingerprints for the four documents X₀, X₁, X₂ and X₃, of FIG. 2 a, are created, and are referred to herein as dX₀, dX₁, dX₂ and dX₃ respectively. Similarly, fingerprints dY₀, dY₁ and dY₂ are created for documents Y₀, Y₁ and Y₂ of FIG. 2 b. The term ‘fingerprint’ is intended to be synonymous with CRC, and sometimes it is used herein to refer to the combined CRC's of both the body text and the normalized subject, since it is this combination that is preferably used for comparison. This combination, of CRC for the body text with CRC for the normalized subject, is also known as the “determiner” for the document.

Having described the compilation of fingerprints for the documents, the process of normalization of text is described.

In one embodiment, before creation of the fingerprint, normalization is applied to the body text and/or subject parameter. The fingerprint would then be compiled from the normalized text. Normalization includes a 1:1 ratio, in which the normalization output is equivalent to the input, and such normalization is ineffective. In this case, the text may be referred to as normalized text, even if no normalization function has been applied to it. However, normalization can also remove features that are not directly part of the body text or subject. For example, for most documents, normalization can be applied to strip all formatting. This includes font, font size, italics, bold, color, etc. For email documents, normalization may also include removing characters that were added by the software document creation program. An example of added characters is the “>” sign typically added by email programs when a user replies to an email. The “>” sign at the beginning of a line indicates that that line of text is copied from the email to which the user is replying. Normalization can also remove headers, footers, attachments and attachment notices, disclaimers, and signatures. Another example of added characters is in the subject parameter of headers. When replying to emails, email programs typically add to the subject line the characters “Re:”, and when forwarding, they add the characters “Fw:” or “Fwd:”. Other characters that are sometimes added to the body text, by email programs include “=20”, added when incorrectly converting from certain email programs to others. Sometimes a vertical line is added on the left to indicate included text from a previous email. Superfluous spaces are sometimes added, tabs, new line, etc. For the purpose of comparison between documents, normalization is applied to the body text and/or subject parameter. However, the original body text and subject parameter text is also preserved.

According to certain embodiments, the presence of signatures, disclaimers, anti-virus lines, free mail program notification (program added text), and attachment notification, can result in the lack of detection of true duplicates. For example, two emails may seem different only because they contain different disclaimers.

Alternatively, two emails may seem to be near-duplicates, when really they are very different, but they contain the same long disclaimer. It has been described above that these parameters may be removed in the normalization process. According to certain embodiments, a further category of normalization is described here. Disclaimers and the like are stripped from the document, and are replaced with a single word or number, unique to each type of disclaimer, signature, etc. This action reduces the influence of a long disclaimer on the rest of the text. Thus two emails whose main texts are not near duplicates will not suddenly appear as near-duplicates due to having identical disclaimers. Yet also two emails that have identical texts with different disclaimers, are related but are not true duplicates, so the presence of the replacement word ensures that the text analysis categorizes them as near-duplicates. According to one embodiment of a method for applying the invention, the method includes removing each of disclaimers, signatures, program added text and attachment notifications from the body text of documents, and replacing each unique disclaimer, signature, program added text and attachment notification with a unique short identifier prior to the creation of the document fingerprint.

In accordance with certain embodiments, there is provided a sequence of operations using normalized fingerprints, to determine equivalence and inclusiveness of documents. The embodiment should not be construed as limiting the invention in any way, as a number of alternative embodiments also exist. For example, other means can be implemented to assign values, or the entire system may use Object Oriented Programming instead of a data structure or database, etc. Data structure details can be organized differently, and may be organized in terms of trees instead of in terms of documents, as described herein. A non-limiting form of data structure is an SQL database, however, the invention does not need to use a data structure in any way. Hence, the following embodiment should not be construed as limiting, but is provided for exemplary purposes only.

Equivalence and inclusiveness may be alternatively accomplished by an individual algorithm, or another method may be used entirely to achieve the intent of the present invention. In one example, all documents can be first expanded into all of their component presumed documents, before comparison. Or, in another example, only the most inclusive documents are identified. Or, in a further example, selected documents from amongst a large group are processed. These selected documents may refer to all of the documents, or a defined subgroup from amongst the documents. Yet the following is a suggested embodiment. It is assumed that the document presented for processing has not yet been searched for header-type text, nor has any normalization yet been applied, nor have fingerprints been created.

The following is a specific example that serves to illustrate a broader concept. The specific example involves certain details that only represent one embodiment of the present invention, and is provided for exemplary purposes only. In accordance with certain embodiments of the invention, a processor is used with associated display, for communicating with the data structure. The processor is capable of manipulating the data of the data structure and displaying selected data on a display unit. With reference to FIG. 3, a document is presented for processing. In the present example, the document involved is an e-mail.

In step 301, the document is assigned a DocID value, and an index of zero. For example, the document may be assigned a DocID of 100.

In step 302, a field is set up for the document being processed, entitled MailID. This is initialized as the DocID of the document.

In step 303, the three identifiers described for the document are stored in a data structure, for example, for a first document, the particulars might be as follows:

DocID MailID Index 100 100 0

In preliminary step 304 a, fields from the e-mail metadata are considered header fields. These include, but are not limited to the following fields: To, CC, BCC, Sent time, Internet Message ID, In Reply Message ID, Subject.

In step 304 b, the abovementioned fields from the e-mail header are parsed, including the fields: From, To, CC, BCC, Sent time, Internet Message ID, In Reply Message ID, Subject, Body, attachments. The parsed information is stored in a data structure.

In step 305, the Subject parameter is normalized and a CRC-MD5 is computed on the normalized subject (Nsubject). Both the subject and the CRC of the normalized subject are stored.

In step 306, a CRC on the normalized body text (Nbody) is calculated.

In step 307, the normalized body CRC and normalized subject CRC are compared with others in a repository for CRCs, and if a matching CRC pair already exists in the repository, the DocID of this document is linked to that of the match, and the document is finished being processed.

Otherwise, step 308, a loop, is accessed. This loop enables multiple presumed e-mails, from the body text of the original email, to be located, indexed, and processed. In step 308 a, the body text of the original email is searched to locate the next presumed email. In step 308 b, if a presumed email is found, the presumed email is provided with identification, and its index is set to one greater than that of the previously processed presumed email. In step 308 c, one is directed to follow again all the steps to process repeatedly the remainder of the body of the email for successive instances of header-type text, as stipulated in steps 303 onwards; for each instance, to construct a presumed document, index it, create a CRC pair, compare it for matching documents, and link if found. In step 308 d, when no more presumed emails can be located within the body text of the original email, the document is finished being processed.

The following table shows the index value that has been assigned to each of three presumed documents that are derived from the original document with DocID of 100.

DocID MailID Index 100 100 0 110 100 1 120 100 2 130 100 3

Note that each document can be derived from the document of next lowest index value. For example, document 110 can be derived from 100 (as indeed it was), and document 120 from 110. Therefore document 100 is inclusive of document 110, and document 110 is inclusive of document 120. Each document is inclusive of the document of the next index value. Additionally, document 100 is inclusive of all documents that are equivalent to document 110. Inclusiveness of documents and equivalent documents is described with reference to FIG. 5.

The following representation details the comparison of documents for equivalence, and also details the construction and comparison of presumed documents, the latter being similar to the above description with reference to FIG. 3. This representation is again a narrow description of a broader concept, and is provided for exemplary purposes only.

In the following representation, a number of documents are to be compared with one another for equivalence. The documents involved are original documents X₀ and Y₀ from FIGS. 2 a and 2 b, as well as an additional two documents P₀ and Q₀. Fingerprints have been created for each of the documents, namely dX₀, dY₀, dP₀ and dQ₀ respectively. None of the documents have yet been reconstructed to find presumed documents within them. With reference now to FIG. 4 a, repository 40 is shown. As can be seen, a number of fingerprints are waiting to be processed. Fingerprint dX₀ is the first of the four fingerprints to be processed. It is inserted into repository 40 for comparison, and, since no equivalent fingerprints are found, fingerprint dX₀ is then stored in repository 40.

With reference now to FIG. 4 b, the text of document X₀ is then searched for presumed documents, and presumed document X₁ is found. Fingerprint dX₁ is created for presumed document X₁. Fingerprint dX₁ is then inserted for comparison into repository 40. Fingerprint dX₁ is also found to have no equivalents and so it is also stored in repository 40. Document X₀ is then searched again, for further presumed documents, and document X₂ is found, for which fingerprint dX₂ is created. Fingerprint dX₂ is inserted for comparison into repository 40. Fingerprint dX₂ is also found to have no equivalents and so it is also stored in repository 40. Document X₀ is then searched for further presumed documents, and document X₃ is found, for which fingerprint dX₃ is created. Fingerprint dX₃ is inserted for comparison into repository 40. Fingerprint dX₃ is also found to have no equivalents and so it is also stored in repository 40. Document X₀ is then searched for further presumed documents and no more are found.

With reference to FIG. 4 c, fingerprint dY₀ is now processed. Fingerprint dY₀ is inserted into repository 40, and compared with all the previously stored fingerprints. It is found to be identical to fingerprint dX₁. As a result of this, fingerprint dY₀ is not stored, but fingerprint dX₁ is registered as being a fingerprint of dY₀ as well as of dX₁. It is noteworthy that it is not necessary to search document Y₀ to find the presumed emails Y₁ and Y₂ that it does in fact include, as shown in FIG. 2 b, since document Y₀ has already been found to be equivalent to document X₁, which has already been expanded.

With reference to FIG. 4 d, fingerprint dP₀ is processed. It is found to have no equivalents, so it is stored in repository 40. Document P₀ is then searched and found to include document P₁, for which a fingerprint dP₁ is created. Fingerprint dP₁ is also inserted into repository 40, found to have no equivalents, and stored. Document P₀ is searched for further expansion possibilities and none are discovered.

With reference to FIG. 4 e, fingerprint dQ₀ is inserted into repository 40, and found to have no equivalents, so it is stored in repository 40. Document Q₀ is then searched and found to include document Q₁, for which a fingerprint dQ₁ is created. Fingerprint dQ₁ is also inserted into repository 40, and found to be equivalent to dP₁. Fingerprint dQ₁ is therefore not stored, but fingerprint dX₁ is registered as being a fingerprint of dY₀ as well as of dQ₁.

With reference to FIG. 5, a suggested sequence of operations is provided for building nodes and trees from compared documents. The compared documents may have been compared by any of a variety of methods, for example, as described with reference to the representation of FIG. 4.

The following sequence of operations is presented in FIG. 5 a, and an example set of documents is shown in FIG. 5 b, relating to the sequence of operations. FIG. 5 c shows the documents of FIG. 5 b arranged into a tree after implementing the sequence of operations of FIG. 5 a. With reference now to FIG. 5 b, two original documents are shown, namely 100 and 200. Each is expanded to produce presumed documents—document 100 is expanded to produce documents having DocID of 110, 120 and 130 respectively, while document 200 is expanded to produce document 210. These document numbers can also be referred to as the document identifiers, or DocID. A MailID of the original and all the derived presumed documents is set as the DocID of the original document from which they were derived. Thus, for example, the MailID of documents with DocID of 100, 110, 120 and 130, are all 100, as is actually shown in the table above, with reference to step 308 of FIG. 3.

With reference once again to FIG. 5 b, each document is displayed as having a normalized body text CRC and a normalized subject CRC. For example, for document 100, these are ‘aa1’ and ‘bb1’ respectively. Each document is assigned a document index according to its relationship with the original document from which it is derived. For example, Document 100 has an index of 0, indicating it is an original document, 101 has an index of 1, etc, as it is the first presumed document located within the body text of document 100, etc. It will be noted that Document 210 has the identical normalized body text CRC and normalized subject CRC to document 120, namely ‘aa3’ and ‘bb3’, although they are derived from different original documents. That is why, in FIG. 5 c, these two documents are associated with the same node of the same tree.

With reference now to FIG. 5 a, in step 501, a field is created in the data structure for each document, entitled NodeID. NodeID represents the node to which the document is to be mapped in the tree, although it does not refer to any specific node in any specific tree. Rather, NodeID represents a value that is the same for all documents that are supposed to be mapped to the same node. All documents that have the same normalized body text CRC and normalized subject CRC should be affiliated with, or associated with, the same node, so they are to be updated to the same NodeID. The NodeID field (for each document) is initially copied from the DocID field of the document. When a document is identified as having the same normalized body text CRC and normalized subject CRC as a prior document, the two nodes are merged, as follows. The NodeID field for one of the documents is updated to the lower value NodeID between the two documents. Updating to the lower value ensures that as documents are added, the NodeID of already updated documents remained constant. Various documents may end up with the same NodeID. For example, document 210 has the same fingerprint as document 120. Document 120 has the lower DocID (since it was processed before Document 210), so the NodeID of document 210 would update to the NodeID of 120, which is a copy of the DocID of document 120. The following table indicates the DocID and the NodeID of the example documents:

DocID NodeID 100 100 110 110 120 120 130 130 200 200 210 120

When a first presumed document is found within an original document, the first presumed document becomes the parent of the original document, because it is assumed to have happened before original document. When a second presumed document is found, it is assigned to be the parent of the first presumed document, since the second presumed document is more embedded than the first presumed document, and it is therefore assumed to have occurred earlier. The node associated with each sequentially derived presumed document (derived from the same document) becomes a parent of the node associated with the previously derived presumed document.

The root of a tree is associated with a node that has no parents. A document with no parent is an original or presumed document that does not include within its text any further presumed documents. In step 502, a field is filled in (for each document), in the data structure, entitled ParentNode. This ParentNodeID indicates which other document is the adjacent node in the root direction on a tree. The root of the tree is the node associated with least inclusive document of the tree—the document presumed to have been the earliest. Initially, ParentNodeID is set for all documents at −1, indicating that the document should be associated with a node having no parents. However, when a parent node is identified for a document, the field of ParentNodeID is updated with the NodeID of the parent node. In the example, the ParentNodeID field for Document 130 is identified as −1. All the other documents take their ParentNodeID according to the document index as reflected in their NodeID. The following table shows the ParentNodeID for each of the example documents:

DocID Parent Node 100 110 110 120 120 130 130 −1 200 120 210 130

In step 503, a field is filled in (for each document), entitled TreeID. This field identifies all documents that should belong to the same tree with the same value. Initially, TreeID for all documents is set as a copy of the NodeID field of the document. Beginning with a document that has a value for ParentNodeID of −1, the TreeID for that document remains as the NodeID. Descendants, or children, of that parent node, as indicated by their ParentNodeID field, then have their TreeID updated to that of their parent node. Then, the next generations of children have their TreeID updated to that of their parent node. In this way, all documents belonging to the same tree have the same node. The following table shows the TreeID for each of the example documents:

DocID TreeID 100 130 110 130 120 130 130 130 200 130 210 130

In step 504, a field can be filled in (for all documents) entitled UNION EQUISET. This field relates to linking trees that are identified as belonging to document sets, to be displayed together, as will be described with reference to FIG. 7. Document sets are two or more trees that one chooses to have linked together. For example one may want to link documents that are near duplicates of one another, or documents that appear to be connected due to the sameness of their Conversation Index (Microsoft Outlook), or In Reply Message ID (Some Unix mail systems).

It is also possible to merge trees that are indicated as similar by the field of UNION EQUISET. In a practical example, if a reviewer wishes to view two documents that are near duplicates of one another, together he may be able to merge the two trees that they are each part of. The two nodes may be placed adjacent to one another, with or without hyperlinks, and the rest of the trees to which they each belong are similarly put adjacent to or merged with each other, as part of the same tree.

In step 505, for documents that have the same TreeID, the lowest value of NodeID is used as an update value for the TreeID. As mentioned before, using the lower value for the update ensures that earlier documents do not get updated, and remain with their assigned values. The following table shows the updated TreeID for each of the example documents:

DocID TreeID 100 100 110 100 120 100 130 100 200 100 210 100

As can be seen from the above table, all the documents have a TreeID of 100, and therefore are in the same tree. FIG. 5 c shows the documents arranged in a tree. Each document is associated with, or represented by, a different node, except for 120 and 210, that share a node. The order of the nodes within the tree follows the fields for ParentNodeID of step 502. Root node 33, contains 130, first intermediate node 34 contains 120 and 210, from which branches second intermediate node 35 containing 110, and first leaf node 36 containing 200. Second leaf node 37, containing 100, branches from second intermediate node 35.

Email messages often contain peripheries, such as disclaimers, signatures, and attachments. In one embodiment of the present invention, these are suppressed prior to creating a fingerprint and comparing fingerprints. However, in another embodiment, they may be included in the CRC, or a CRC for these may be used as well. In addition, even if not used for purposes of document creation, these peripheries may be affiliated with the node containing the document to which they pertain, for a reviewer to access.

The following description relates to certain embodiments of the present invention, in which there is provided a method to arrange the aforementioned documents and presumed documents into groups according to their degree of inclusiveness, and according to their equivalence with other documents. Generally speaking, the groups are in the form of trees, as will now be described with reference to FIG. 6. However, the aforementioned documents can alternatively be arranged in the form of columns or lists, or simply individual documents can be selected for perusal, as will be described with reference to FIGS. 8 d and 8 e.

With reference to FIG. 6 a, the output of the data structure is presented as a representational tree consisting of connected nodes. The tree may be a part of the data structure or communicated from the data structure to another unit, etc. Root node 83 is associated with a document that has body text that is not inclusive of the body text of any other document. Each intermediate node 84 is associated with a document that has body text that includes all the body text of the previous node, from the root direction. Leaf node 85 is associated with an inclusive document, having body text that includes all the body text from the string of nodes between root node 83 and leaf node 85.

By way of example, if the documents of FIG. 1 were arranged in a tree, FIG. 1 a would be associated with a root node 83, FIG. 1 b with an intermediate node 34, and FIG. 1 c, with a leaf node 85. However, it is to be noted, that a tree may consist of only a single node, if the document associated with the single node has no included documents. In this case, the single node is both the root node and the leaf node.

As shown in FIG. 6 a, there may be several branches to the tree. In FIG. 6 a, the following three sets of nodes each represent a branch: Nodes 83, 84, 85, 86, 87, Nodes 83, 84, 85, 88, 89, 90, and Nodes 83, 84, 85, 88, 89, 91. Each of the three branches begins with root node 83, and each culminates in a leaf node 87, 90, 91. Such branching occurs when several different documents are all inclusive of a common body text. In the current example, all the three branches include root node 83 and nodes 84 and 85. The documents that are associated with these nodes have body text that is shared by all of the more inclusive nodes 86-91. A node that features immediately adjacent to an arbitrary first node, in the root direction thereof, is termed the parent node of the first node.

The tree is designed to organize the documents into linked nodes. Each node is associated with a group of documents that are equivalent, or at least substantially so (for example, they may have characters that are removed in the normalization of the subject procedure). Links between nodes imply that the text of a document associated with a node on the leaf side of the link includes the text of a document associated with a node on the root side of the link. For example, the text of the document associated with node 86 includes the text of the document associated with node 85.

According to certain embodiments of the present invention, the data structure is arranged in the form of trees, and a tree is defined as a set of directionally interlinked nodes. Each node is associated with at least one document, and all documents associated with a given node have substantially the same body text. Also, all documents having substantially the same body text are associated with the same node. The directional interlinkage indicates that if a first node is a descendent of a second node, the body text of each document associated with the first node is substantially inclusive of the body text of each document that is associated with the second node. For example, node 86 is a descendant of node 85, and the document associated with node 86 is substantially inclusive of the body text of any and all documents that are associated with node 85. The second node is a parent node of the first node. In the example just given, node 85 is termed the parent node of node 86.

The root node of a tree (83) is the ultimate parent of the tree, having no parents itself. In different trees, the root node may have one or more descendant nodes, (descendants include intermediate and root nodes) or a root may have no descendants. In FIG. 6 a, root node 83 has 8 descendent nodes (84-91). There may be several generations of descendant nodes, for example both an intermediate node and a leaf node together provide two generations of descendants. In FIG. 6 a, there are 5 generations of descendant nodes (1st generation: 84, 2nd generation: 85, 3rd generation: 86 and 88, the 4th generation: 87 and 89, and 5th generation: 90 and 91). Also, there may be several same generation nodes, for example there may two parallel branches of nodes branching off a parent node. In FIG. 6 a there are several sets of same generation nodes, for example the 3rd generation has two same generation nodes: 86 and 88, the 4th generation also has 2 same generation nodes: 87 and 89 and the 5th generation has 90 and 91.

With reference now to FIG. 6 b, the documents whose fingerprints are in repository 40 of FIG. 4 c, are organized and presented according to trees. Presumed documents are arranged relative to the original document from which they are derived, by being placed in the root direction of more inclusive documents. When two documents share a common root, it is implied that they both contain the body text of the root. Hence, any presumed document will automatically be placed in the root direction of the document from which it is derived.

In one embodiment, presumed documents are ‘put into’ or associated with the same tree as the original document from which they are derived, the root node is the smallest presumed document, that is, the last one to be derived from the original document. The other presumed documents are arranged in the root direction (ie, towards the root) according to their degree of inclusiveness. As a result, a node is associated with a document that has all the body text of all the other nodes in the direction of the root. In addition, documents that are equivalent, that is, they have the same body text and subject line, as determined by the document fingerprints, share a node. In this way, more complex trees can be created than simply by stringing together trees according to their original composition within a document. It is to be noted that in another embodiment, presumed documents are not associated with nodes, they are only used in order to determine the nodes that other documents, that are equivalent to the presumed documents, should be associated with. However, in a further embodiment, also presumed documents are associated with nodes, sometimes forming a ‘missing link’ when no original email is equivalent to them.

In the present example shown in FIG. 6 b, there is only one tree, containing four nodes 92-95.

In one embodiment, root node 92 links to, (also termed: “is affiliated with” or otherwise displays) the body text and subject line (non-normalized) of document X₃. Root node 92 is also affiliated with certain header parameters of document X₃, taken from the header or metadata of the document, and arranged in a table for easy perusal. First intermediate node 93 (adjacent root node 92) contains the body text and subject line of document X₂, and is affiliated with header parameters from document X₂. Second intermediate node 94 contains the body text and subject line of document Y₀, and is affiliated with header parameters of both documents Y₀ and X₁. Leaf node 95 contains the body text and subject parameter of document X₀ and is affiliated with header parameters of document X₀. The header parameters may be affiliated by means of hyperlinks to the original document, or the header parameters may be copied into a hyperlinked or otherwise affiliated table.

It will be noted that only two of the nodes are associated with original documents, that is, second intermediate node 94, associated with document Y₀, and leaf node 95, associated with document X₀. The fact that a single tree includes nodes associated with two different original documents, namely Y₀ and X₀, indicates to a reviewer that the contents of the two documents X₀ and Y₀ are related. Since they occur along the same thread within the tree, the reviewer can see that document X₀ contains all of the text of document Y₀ as well as some additional matter.

With reference now to FIG. 6 c, a third tree is shown, displaying nodes for the remaining documents whose fingerprints feature in repository 40 of FIG. 4 e. The tree consists of just three nodes, that is, one root node 96 and two leaf nodes 97 and 98. Each leaf node (97 and 98) contains the body text and subject parameter of an original document, namely P₀ and Q₀. Root node 96 contains the body text and subject parameter of presumed document P₁, and also supplies affiliations to header parameters of both documents P₁ and Q₁. Thus two original documents are associated with nodes that are connected into a single tree by virtue of their common included presumed document. This single tree indicates to a viewer that the contents of the two documents P₀ and Q₀ includes identical body text, and that they are likely to be related to a similar subject matter. Thus such a tree increases a viewer's comprehension, compared with viewing the documents as isolated events.

In accordance with certain embodiments of the present invention, additional features of a tree and its construction relate to the fact that emails can be linked into a tree even if they have different subject parameters from one another. The factors that determine if nodes are joined to form a tree include descent, and equivalence of the associated document. It is possible for a user to have changed the subject line of an email in the course of a correspondence. However, if a more inclusive email exists, this can be expanded into a selection of presumed emails, in which the earlier dated ones will have the first subject line, and the later dated ones will have the second subject line. The presence of the more inclusive email indicates that although the subject line has changed, the documents are nevertheless part of a single conversational thread. The more inclusive email is expanded into a set of presumed documents that remain indexed together. As a result, the presumed documents—and all the documents that duplicate to them, are joined into the same tree. Thus, although the subject line of some of these documents is one thing, and the subject line of other of these documents is another, they are nevertheless presented on the same tree, as they were part of the same thread, as indicated by the more inclusive document's expanded contents.

Another benefit of an embodiment of the tree presentation of documents is that a reviewer probably does not wish to read through duplicated documents twice. He can read just one copy or just the subject and body text of a document associated with the node, in response to clicking on a node, if the node is represented on a display as a clickable icon. Or if the node is not a clickable icon, it may give other written directions or a different form of affiliation to the document text. In addition, the reviewer may still have access via the node to a hyperlink to metadata of all the original equivalent documents. If the node is associated with only a presumed document, the node can affiliate to metadata from the presumed documents too (or the node may simply be suppressed from view, as preferred).

In accordance with certain embodiments of the present invention, header parameters of equivalent documents grouped into a table and accessed from the associated node make it particularly easy for a reviewer to compare header parameters and/or statistics between the different copies of ostensibly the same document. For example, he may see which copy is recorded as having been sent first, find out if there are date discrepancies (perhaps one copy of the same email was sent on different days to different people), and find out who recipients of documents are, and more. All this information is available and can even be presented as a list or a table for easy comparison between parameters. Yet in some instances, this information is not required. Therefore, in a further embodiment of the present invention, all metadata is hidden from casual view and presented only upon clicking on an icon or similar reference.

In some cases, a reviewer wishes to have access to all body texts and subject lines, but does not wish to spend time reading anything twice. For example, if the contents of one document are all included within a second document, the reviewer may prefer to be able to read only the inclusive document. Certain embodiments of the present invention provide that documents are organized and presented according to trees, as described above, enabling the reviewer to selectively read only the leaf node, and he will be assured that he has accessed all the content for the documents associated with all nodes leading to that leaf. Additionally, a processor may be configured to indicate on a display unit which nodes are the leaf nodes. For example, leaf nodes may be marked or highlighted, so that the reviewer should know which to read. Additionally, in response to a user command, the processor can be configured to mark nodes for the display unit, in order to indicate whether a thread has been read, the relevance or priority of the thread, or the level of importance of the thread. The processor may further be configured to allow reviewer comments to be added to the display unit.

An additional embodiment of the present invention includes a ‘Leaf Compare’ tool—that is, a text comparison tool that compares between the text of the emails associated with two different nodes, for example between two leaves of the same tree. Using the leaf compare tool, a reviewer can access just the differences between two leaves, without having to re-read the content common to both leaves. The text compare tool may be similar to standard document compare tools, or application specific. It preferably enables three different text formats, indicating deleted text (that is, text from a first node that does not appear in a second node), added text (that is, text from a second node that does not appear in a first node), and common text (that is, common text to both nodes), between two (or more) leaves. Examples of different text formats include but are not limited to, red strikeout text for deleted text, blue underlined text for added text, and plain black text for common text.

In accordance with a further embodiment of the present invention, the presentation of the tree may additionally indicate which nodes are associated with original documents, and which nodes are associated with presumed documents. For example, nodes associated with only presumed documents may be colored a different color, italicized or grayed. In a different embodiment, a node that is associated with both a presumed document and also an original document will only display an affiliation with the original document, while the affiliation to the presumed document is suppressed from view. In this way, readability is enhanced.

In a further embodiment, the whole tree structure is suppressed from view (or is not created). In this case, groups of documents that each contain a common presumed document are identified. This identification can be made using the algorithms disclosed in this disclosure, or another method. The documents from the group that are the most inclusive are identified and displayed for review. For the purposes of this embodiment, the relationship between the other documents does not need to be determined. This is described with reference to FIG. 8 c.

In a further embodiment of the present invention, documents are not only compared for equivalence but also for near-duplication. A suggested algorithm for determining near duplication may be found in co-pending application: U.S. application Ser. No. 11/572,441, whose contents are incorporated herein by reference. Determining that documents are near-duplicates of one another, enables near-duplicate documents to be presented to a reviewer as such. This is very useful for a number of reasons. Firstly, documents that are near duplicates of one another usually refer to the same subject matter, so it is convenient to review them side by side. Secondly, documents that are near-duplicates very often actually begin as identical documents, and are changed in minor ways, by the user, or, inadvertently, by a computer program. Thirdly, the level of near duplication can be variable by a user, enabling the user to define how close to each other two documents need to be in order for them to qualify as near-duplicates, and for the user to have them presented together for review. Fourthly, near-duplicates can pick up the similarity between two documents when the second document is basically identical to the first, but has had added comments interspersed amongst the text. For example, in an email reply, sometimes a user adds a word like “yes” somewhere in the middle of the body text of the email. This additional word can prevent the two documents—the email reply, and the email to which it is replying—from being strung together on the same tree. Yet the process steps for near duplication can indicate that the rest of the text is basically identical, which can help a reviewer understand the relative context of the two emails.

The following represents the use of comparison for near duplication, in accordance with an embodiment of the present invention. In the process of comparing the documents for duplication, the documents are also compared for near-duplication. At least a portion of the body text of each document is compared for near-duplication with at least a portion of the body texts of other documents. The comparison enables the detection and indication of near-duplicated documents. If near-duplication is found, an association is created between the documents found to be near-duplicates of one another. In accordance with a further embodiment, nodes that are associated with documents that are near duplicates to one another are assigned to the same document set. All other nodes in the trees that contain the near-duplicated nodes, are similarly assigned to that document set, as will be shown with reference to FIG. 7 below. In accordance with a further embodiment, a user is enabled to define the degree of similarity between documents for the documents to be considered as being closely duplicated.

In accordance with certain embodiments, documents determined to be near-duplicates of one another, are not presented as the same node on the same tree, but are presented in combination, that is, in close proximity to one another on a display unit as shown, or otherwise electronically linked to one another. The link indicates the fact that the two trees each contain a node, that are associated with documents that are near-duplicates to one another. For example, a tree has a set of nodes which may be presented on the top section of a computer screen. A document that near-duplicates to any of the nodes of the tree is presented as an individual node directly below the node to which it near-duplicates. Sometimes, a document that near-duplicates to a document in a tree, is itself part of a different tree. In this case, the two trees can be both presented to a reviewer together, and are called a ‘document set’. With reference now to FIG. 7, a computer display 50 shows two different trees, each having a root node 73, intermediate nodes 74, and leaf nodes 75. Each of the two trees contains a node that is associated with documents that near-duplicate to one another. The two nodes that are associated with the near-duplicate documents are marked ND. The trees that have nodes that are associated with near-duplicate documents are displayed together to a reviewer, as for example, is shown in FIG. 7, in which the two trees are presented on the computer display 50 simultaneously. The two trees in this non-limiting example are presented one above the other, separated by separating line 52, to indicate that the nodes displayed are not all part of the same tree, but that the displayed trees are related to one another, and part of a single document set. A document set consists of two or more related trees or nodes.

Document sets are another example of data structure. Document sets may be sets of nodes or sets of documents according to their association with nodes. In accordance with an embodiment of the invention, a method for marking the documents as associated with a certain document set is as follows: a first document is associated with a document set; all documents that are associated with a node that is linked to the node associated with the first document (or another previously added document) are then also associated with the document set. All documents that near-duplicate to a document already in the document set are also associated with the document set.

In the present example, the related trees are connected by the fact that one or more nodes near-duplicate to each other between the two trees. The two trees are displayed in close proximity to one another. This is just one specific way of indicating that the nodes associated with near duplicate documents are affiliated with one another. This is only one form of representing the relationship between near duplicates and there are many other acceptable ways to represent them, considered within the scope of the present invention.

In a further embodiment of the present invention other forms of document sets are described, enabling two or more trees to be affiliated with one another, indicating that they probably contain related subject matter. In a case where the documents are emails, there are email programs that store message identifiers to identify individual emails with a string of characters. When a user presses Reply-to, or Forward, in order to construct his email based on a previous email, these email programs create the message identifier for the new email to include a reference to the previous email. By parsing the message identifier, it is possible to determine which emails are replies or forwarding of which other emails. These emails are likely to be related to one another, so such emails are grouped together in a document set. In other words, emails whose Message ID indicate that they are connected to one another are not strung together on the same tree, but the trees in which each of them are nestled are presented together on the screen.

In a further embodiment of the present invention, document sets are constructed based upon a Conversation ID. Conversation ID is a feature of Microsoft Outlook, and is similar to the Message identifier described in the previous paragraph. Basically a Conversation ID contains a string of characters identifying an email. The basic character string for a new email may be 44 bytes long. When a person replies to, or forwards the email, an additional 10 bytes are added to the 44 byte string. Thus it is easy to see which emails are replies to other ones. Documents identified as being related to one another based upon Conversation ID are presented as document sets. The fact that their subject matter is likely to be related is indicated to the reviewer by the presentation of two or more trees in close proximity, or linked to one another. In accordance with one embodiment, a method for the invention includes creating an association between nodes that are associated with documents having related Conversation ID or Message ID indicators. The documents may be displayed grouped according to document sets.

The above description describes the use of trees and nodes in representing duplicating documents, parent-child relationships, and near duplicates. The following description relates to different types of trees. In FIG. 8 a, a (prior art) tree of documents is shown, such as may be created with the Prior Art of constructing a tree solely using Conversation ID Trees, of Microsoft Outlook. The tree is created for an occurrence known as Scenario 1, as follows. Scenario 1 represents the following exchange of emails. Document a is a first email sent by a sender to three recipients. Documents b, d, and f, are three identical replies from the three recipients. This can happen for example if the sender had asked them to respond with a “yes” or a “no”. Various metadata fields such as the “from:” field parameter, are different between the three identical, or duplicate, emails b, d and f, yet the body texts are substantially identical. Documents c and e are two different, responsive, further replies, from the sender to two of the three recipients. All of these documents have been extracted from the sender's email program, and arranged into a tree.

As may be seen in FIG. 8 a, each email is associated with a different “node”, or icon on the tree, since these icons by definition for this prior art only contain one document. There are therefore six nodes, or icons, on the tree, namely 851-856, showing the exchange. For purposes of simplicity, it has been assumed in Scenario 1 that the subject line was not changed during the exchange of emails, and that only the emails from the sender's computer are available. Note that even if there would have been a thousand different email replies instead of just three (b, d, and f), the tree would have had been massive to accommodate the thousand different nodes, or icons, one per document.

In FIG. 8 b, a tree of nodes according to certain embodiments of the present invention is shown. The same documents from Scenario 1 are organized, but this time the tree need only contains four nodes, namely (861-864), associated with the four different emails. Node 861 is associated with document a, Node 862 is associated with documents b, d, and f, Node 863 is associated with document c, and Node 864 is associated with document e. The tree of Figure Ab is significantly more compact than that of Figure Aa, since it contains fewer nodes. This reduces the representational space on the display that is required, and also slashes review time for a reviewer.

In FIG. 8 c, a tree having only a trunk and leaf nodes, according to a different embodiment of the present invention, is shown. As mentioned above, according to certain embodiments, another output of the present invention is when all documents containing the same included document are identified as a subgroup. From this subgroup of documents, the documents that are most relevant may be the inclusive documents. These are therefore associated with leaf nodes on a tree. In the trunked tree, as shown in FIG. 8 c, all the non-inclusive documents are not displayed as nodes, but are all grouped together into the trunk. A table affiliating the documents and their header parameters may certainly be provided. The only nodes that need be shown for the trunked tree are the leaf nodes. In FIG. 8 c, the same documents from Scenario 1 are organized, but this time, there is only one trunk 871 and two leaf nodes 872-873. The trunked tree may be built according to a method described above for building nodes and trees, while not differentiating between nodes except leaf nodes, or using another method entirely. The trunked tree can have associated with the trunk a number of documents having different subject parameters, so long as all include the same included document (whether original or presumed). It has been described above the characteristics that determine whether a document is considered included within the body text of another.

According to this embodiment, the data structure comprises one or more trees, in which a tree comprises at least a trunk and at least one node. Each node is associated with a document, and the trunk is associated with (zero or more) documents. All documents whose body text includes the same included document are associated with the same tree, and each unique inclusive document, as well as documents that duplicate to this unique inclusive document, is associated with one of the nodes of the tree. Each included document, as well as documents that duplicate to included document, are associated with the trunk of the tree.

One method for producing the trunked tree is using the embodiments described above with respect to FIGS. 3-6. When the tree is built, any nodes that are associated with documents that match presumed documents, or are associated directly with presumed documents, are associated with a trunk 871—these are the documents for which a more inclusive document exists. According to an embodiment of the invention, the trunk is suppressed from view, or, alternatively, it is displayed.

In one embodiment, in order to preserve header parameters associated with parent nodes, the header parameters of all the documents associated with the trunk are associated with the leaf nodes. In other words, if a document associated with the node has had a presumed document constructed from it, one can additionally affiliate header parameters from all the documents that matched the presumed documents with the node. This is because the nodes associated with the presumed documents have been suppressed from display.

In accordance with a further embodiment of the present invention, another form for outputting documents, that have been arranged according to inclusiveness, is provided, as opposed to presenting them as trees. The trunk or the nodes may be displayed with one of many forms of tree symbolism; yet display alternatives also exist, as will be shown. Documents associated with the trunk or the node are identified as being grouped according to their association with the trunk or tree, but do not have to be presented in terms of the group.

As shown in FIG. 8 d, according to this embodiment, a subset of documents from the original group of documents is presented. The documents are not necessarily displayed in their entirety; they may just be provided as a list, as shown in the first column of FIG. 8 d. The subset includes only a single copy of the inclusive documents, that is, Documents c and e. In other words, the subset includes all the original documents, except those documents that are duplicate of a presumed document, and it also excludes all presumed documents. In accordance with one embodiment, the documents that do not exhibit in the subset (i.e., they are suppressed) are nevertheless available for a reviewer to see, if such is desired. For example, these non-exhibiting documents can be affiliated with the documents of the subset to which they duplicate, or from which a presumed document to which they duplicate is derived or constructed. Or, according to another embodiment, all the nodes are displayed in a subset, while nodes associated with presumed documents are suppressed from the subset display. In this way, all included emails, (these are the documents that are associated with presumed documents) are not shown in the subset display. In a further embodiment, header parameters for each document associated with a displayed node of the subset are shown in a data table of the node. Header parameters for each document associated with a suppressed node from the subset are also shown in the data table of the displayed node of the tree. The displayed node with which the data table of suppressed nodes is associated is the node that is associated with the document from which the presumed document associated with the suppressed node is constructed, i.e. the inclusive node.

In another example, shown in FIG. 8 d, a further column is added, listing and linking (affiliating) all the included documents with the inclusive document that they are included in. According to further embodiments of the invention, other details are added to the list of inclusive documents, for example, an indicator that one of the documents had an attachment. According to a further embodiment of the invention, if a duplicate to an inclusive documents exists, this duplicate would be listed in the same cell as the inclusive to which it duplicates. For example, the cell entry might be “c,h,”, in which h is a duplicate to c, an inclusive document. According to an embodiment therefore, a processor is configured to display the documents as a list of grouped entries, in which each grouped entry includes the documents associated with a leaf node, a leaf node being a node that has no descendant nodes. These documents are the inclusives. The documents can be referred to with their numeric identifiers. In a further embodiment, each grouped entry further includes a listing of the documents associated with nodes of which said leaf node is a descendant.

In accordance with another embodiment of the present invention, another form for outputting documents, that have been arranged according to inclusiveness, is provided, as opposed to presenting them as graphical trees. For example, documents may simply be listed in the data structure in sequential order and be supplied with a column listing indicating with which tree, and with which section of the tree, they are associated. As shown in the first column of FIG. 8 e, all the documents of the original group are listed in a data structure, for example in a first column. A notification is provided in the third column, adjacent to the list, to indicate which documents are the inclusive documents. In accordance with another embodiment, and as shown in the second column of FIG. 8 e, further indication indicates the position a node for the document would assume if it were to be displayed upon a tree. For example, the node address for document b, d and f, is 10:10:11. They all have the same node address because they are duplicating documents. The node address indicates that they feature in Tree 10, in Thread 10, and in Position 11. These numerical values for tree, thread and position need not necessarily start with 1, for example, Thread 10 may be the first thread of the tree. According to a further embodiment, another parameter can be added to the address, to indicate which document set the tree belongs to. According to certain embodiments the columns can be sorted by a user, for example, if the data structure is in the form of a spreadsheet, they may be able to be sorted according to one of more of the following criteria: document identifier, document sets, numeric node address, an inclusive flag, and also, a ‘first copy of an inclusive flag’. This latter flag would direct a reviewer to read only one (arbitrary) copy of the inclusive.

In another example, the columns could represent trunked trees as shown in FIG. 8 c, and the address column would indicate the tree to which the document is associated and whether it is associated with a root node or the trunk. These examples are only intended for exemplary purposes, and do not seek to limit the number of ways that numerical or written indicators are able to describe the arrangement of a document relative to others, arranged according to duplication and inclusiveness.

There have been described above, many non-limiting different ways in which documents can be arranged according to duplication, inclusiveness, and, according to certain embodiments, according to document sets. The following seeks to describe document properties and document sources that can be used in accordance with embodiments of the invention.

Another benefit of an embodiment of the present invention is its ability to have access to files such as emails from different computers, or from different email archives, for example different PST files. According to certain embodiments, the operation of the invention is not to immediately assign documents extracted from different bulk files to different trees, but rather assigns documents to trees according to inclusiveness, irrespective of which file the document originated from. Thus a tree may be composed of documents originating from a number of different trees. According to further embodiments, it is also irrelevant whether the documents were in whole document format or needed extraction to document format before the invention is applied. Similarly, the invention is not limited to only associating documents with nodes on the same tree if the subject parameter for all the documents is the same. On the contrary, for different nodes, the subject parameter may be different, but as long as the documents satisfy the inclusiveness condition, they may be associated with nodes of the same tree.

FIG. 9 shows 2 computers, 130 and 132, from which many documents are to be extracted and organized. For example, each computer contains a PST file, 134, 136. Each PST file contains, or has available for extraction, many email documents, or emails for short. Array 138 shows how these files can theoretically be stored all together, irrespective of which PST they are extracted from. In certain embodiments, array 138 is included. In other embodiments, the array does not need to exist, although the documents may still be extracted from multiple sources. Tree 140 shows how the files from array 138, originating from each of the computers, are together organized as a tree or trees, according to their degree of inclusiveness. Tree 140 includes one or more nodes, each node associated with one or more documents, for example emails.

As mentioned before, according to certain embodiments, a node can even be associated with a “presumed document”—or a “presumed email”—an document that has not been extracted from either of the PSTs 134 or 136, but is nevertheless presumed to have existed once, since a header for it, and text, is included within the text of a document that is found in one of the PSTs.

As mentioned, Tree 140 includes a number of nodes 142, and each node is associated with one or more documents. Each document is associated with its own node, unless the document duplicates to another document. If the document is a duplicate of another document, both of them are associated with the same node. Each node forms its own tree, unless it is a descendant of a different node. From the contents of more than one PST, it is expected that a high number of different trees will be used to organize the documents. A node belongs to a tree if it is a descendant of another node in the tree.

It will also be understood that the system according to the invention may be a suitably programmed computer. Likewise, the invention contemplates a computer program being readable by a computer for executing the method of the invention. The invention further contemplates a machine-readable memory tangibly embodying a program of instructions executable by the machine for executing the method of the invention.

Many specificities have been provided in the above description, however, these should not be construed as limiting the invention in any way. In addition, certain details have not been described, as they would be obvious to persons skilled in the art.

The invention should be understood in terms of the appended claims. 

The invention claimed is:
 1. A computer implemented method for organizing documents into nodes, in which a node represents a group of near equivalent documents, said computer implemented method comprising: (i) providing a plurality of original documents, each of the original documents comprising a header and a body text, and wherein said header comprises at least one header parameter and wherein said body text comprises text; (ii) selecting a document from among said plurality of original documents and associating the selected document with a node; (iii) comparing a fingerprint of said selected document to previously stored fingerprints of other documents from amongst said plurality of original documents, and in the case of a match between the fingerprints, merging the node associated with said selected document with a node associated with a matching document having a fingerprint matching the fingerprint of said selected document; (iv) searching in text order through said body text of said selected document to locate a first instance of header-type text within said selected document, wherein said header-type text contains at least one header parameter; (v) constructing a presumed document from a subset of the body text of said selected document, the constructed presumed document having (a) a header that includes one or more parameters from said header-type text located within said body text of said selected document, irrespective of whether the subject parameter of the header of said presumed document is the same as the subject parameter of the header of said selected document, and (b) body text that includes the text of said selected document located after said header-type text in said body of said selected document, and associating said presumed document with a node; (vi) comparing a fingerprint of said presumed document to the previously stored fingerprint of at least one other document from among said plurality of original documents and in the case of a match between the fingerprints, merging a node associated with said presumed document with a node associated with a matching document having a fingerprint matching the fingerprint of said presumed document; and (vii) if the comparing of (vi) does not result in a match, processing repeatedly a remainder of the body text of said selected document for successive instances of header-type text according to step (iv), and for each successive instance of the header-type text, constructing a corresponding presumed document according to step (v), and comparing for any matching documents to the corresponding presumed document according to step (vi), said processing of steps (iv)-(vi) is repeatedly performed until a match is found in step (vi) or until no new instances of header-type text are found in step (iv), wherein each fingerprint comprises a representation of a corresponding document, and the plurality of nodes are arranged in terms of more than one tree, each tree comprising at least one node from the plurality of nodes, each tree comprising at least a root node and at least a leaf node, a root node being a node that is not a descendant of any other node, and a leaf node being a node that has no descendent nodes, a node not being prohibited from being both a root node and a leaf node, all nodes that are descendant from the root node are contained by the tree, each node being associated with either: (1) one of the original documents and any matching document thereof or (2) one of the presumed documents and any matching document thereof.
 2. The computer implemented method of claim 1, further comprising: (viii) storing the document fingerprint for future comparison with other document fingerprints.
 3. The computer implemented method of claim 2, further comprising: displaying on a display unit symbols indicative of said nodes, and affiliating for each node a body text and subject parameter of at least one document associated with the node.
 4. The computer implemented method of claim 3, further comprising: affiliating each node with a plurality of header parameters from each document associated with the node, said plurality of header parameters being arranged in a table.
 5. The computer implemented method of claim 4, wherein said documents are emails and wherein said plurality of header parameters comprises two or more fields from an email header selected from the group of fields consisting of: “To”, “From”, “Subject”, and “Date”.
 6. The computer implemented method of claim 2, further comprising: displaying the nodes; and suppressing nodes associated with a presumed document from the display.
 7. The computer implemented method of claim 6, further comprising: affiliating each displayed node with header parameters of each document associated with said displayed node; and affiliating header parameters of documents associated with suppressed nodes with a node associated with a document from which the presumed document associated with said suppressed node is constructed.
 8. The computer implemented method of claim 2, wherein (ii) further comprises comparing for near-duplication at least a portion of the body text of said selected document to at least a portion of the body texts of other documents from amongst said plurality of documents.
 9. The computer implemented method of claim 8, further comprising: creating an association between nodes that are associated with documents found to near-duplicate to each other.
 10. The computer implemented method of claim 9, further comprising: enabling a user to define a degree of similarity between documents for documents to be considered near-duplicating.
 11. The computer implemented method of claim 8, further comprising: associating documents with document sets by associating to a document set: a first document, and documents that are associated with a node that is linked to the node associated with said first document already associated with said document set, and documents that near-duplicate to a document already associated with said document set.
 12. The computer implemented method of claim 2, further comprising: creating an association between nodes that are associated with documents having related Conversation ID or related Message ID indicators.
 13. The computer implemented method of claim 2 further comprising: removing at least one member of the group consisting of: disclaimers, signatures, program added text and attachment notifications from the body text of documents, and replacing unique text of each removed member with a unique short text identifier prior to said comparing in (ii), wherein said fingerprint of (iii) is a fingerprint of said body text after said replacing.
 14. The computer implemented method of claim 2, further comprising: displaying documents in a data structure able to be sorted according to one or more members of the group consisting of: document identifier, document set, node address, inclusive flag, first copy of an inclusive flag.
 15. The computer implemented method of claim 2, further comprising: (ix) if a document is found to be a duplicate of a prior document, suppressing step (viii).
 16. The computer implemented method of claim 15, further comprising: (x) forming a subset of a large number of documents by including each document into the subset except for documents that duplicate to another document already in the subset, and except for documents that duplicate to a presumed document whereby only a single copy of inclusive documents are in the subset.
 17. The computer implemented method of claim 16, further comprising: affiliating each document in said subset with other documents that duplicate to said document and with documents that duplicate to a presumed document derived from said document.
 18. The computer implemented method of claim 1, wherein (ii) is applied to selected documents from amongst said plurality of original documents.
 19. The computer implemented method of claim 1, wherein said (ii) further includes creating a fingerprint for each of at least a portion of a normalized body text and a normalized subject parameter of said selected document, said normalized body text and said normalized subject parameter are processed from said body text and a subject parameter of said header parameters, said (iii) includes comparing the created fingerprint of said selected document to previously stored created fingerprints of other documents from amongst said plurality of documents, and in the case of a match, merging the node associated with said selected document with a node associated with the matching document, wherein said comparison for detecting and indicating duplicating documents; and said (vi) includes creating a fingerprint for each of at least a portion of the normalized body text and the normalized subject parameter of said presumed document and comparing the created fingerprint of said presumed document to a previously stored created fingerprint of at least one other document from among said plurality of documents and in the case of a match, merging a node associated with said presumed document with a node associated with the matching document.
 20. The computer implemented method for organizing documents of claim 19, further comprising a step of linking nodes, in which linking implies that the normalized body text of a document on a first side of said link is inclusive of the normalized body text of a document on a second side of said link, and wherein (vi) further comprises linking the associated node to be a parent of the node stipulated in (iii); and wherein (vii) comprises linking the associated node to be a parent of the associated node of the most recent iteration of (vi).
 21. The computer implemented method of claim 1, wherein said (vii) includes: for each of said instances, constructing said corresponding presumed document irrespective of whether the subject parameter of the header of said corresponding presumed document is the same as the subject parameter of the header of said original selected document or of previous constructed presumed document.
 22. A non-transitory computer program product comprising a storage storing computer code for performing a method for organizing documents into nodes, in which a node represents a group of near equivalent documents, the computer program product comprising: (i) a computer code portion for providing a plurality of original documents, each of the original documents comprising a header and a body text, and wherein said header comprises at least one header parameter and wherein said body text comprises text; (ii) a computer code portion for selecting a document from among said plurality of original documents and associating the selected document with a node; (iii) a computer code portion for comparing a fingerprint of said selected document to previously stored fingerprints of other documents from amongst said plurality of original documents, and in the case of a match between the fingerprints, merging the node associated with said selected document with a node associated with a matching document having a fingerprint matching the fingerprint of said selected document; (iv) a computer code portion for searching in text order through said body text of said selected document to locate a first instance of header-type text within said selected document, wherein said header-type text contains at least one header parameter; (v) a computer code portion for constructing a presumed document from a subset of the body text of said selected document, the constructed presumed document having (a) a header that includes one or more parameters from said header-type text located within said body text of said selected document, irrespective of whether the subject parameter of the header of said presumed document is the same as the subject parameter of the header of said selected document, and (b) body text that includes the text of said selected document located after said header-type text in said body text of said selected document, and associating said presumed document with a node; (vi) a computer code portion for comparing a fingerprint of said presumed document to the previously stored fingerprint of at least one other document from among said plurality of original documents and in the case of a match between the fingerprints, merging a node associated with said presumed document with a node associated with a matching document having a fingerprint matching the fingerprint of said presumed document; and (vii) a computer code portion for determining if the comparing of (vi) does not result in a match, processing repeatedly a remainder of the body text of said selected document for successive instances of header-type text according to step (iv), and for each successive instance of the header-type text, constructing a corresponding presumed document according to step (v), and comparing for any matching documents to the corresponding presumed document according to step (vi), said processing of steps (iv)-(vi) is repeatedly performed until a match is found in step (vi) or until no new instances of header-type text are found in step (iv), wherein each fingerprint comprises a representation of a corresponding document, and the plurality of nodes are arranged in terms of more than one tree, each tree comprising at least one node from the plurality of nodes, each tree comprising at least a root node and at least a leaf node, a root node being a node that is not a descendant of any other node, and a leaf node being a node that has no descendent nodes, a node not being prohibited from being both a root node and a leaf node, all nodes that are descendant from the root node are contained by the tree, each node being associated with either: (1) one of the original documents and any matching document thereof or (2) one of the presumed documents and any matching document thereof.
 23. A system for organizing documents into nodes, in which a node represents a group of substantially near equivalent documents, the system comprising: a memory; and a processor configured to perform at least the following: (i) providing a plurality of original documents, each of the original documents comprising a header and a body text, and wherein said header comprises at least one header parameter and wherein said body text comprises text; (ii) selecting a document from among said plurality of original documents and associating the selected document with a node; (iii) comparing a fingerprint of said selected document to previously stored fingerprints of other documents from amongst said plurality of original documents, and in the case of a match between the fingerprints, merging the node associated with said selected document with a node associated with a matching document having a fingerprint matching the fingerprint of said selected document; (iv) searching in text order through said body text of said selected document to locate a first instance of header-type text within said selected document, wherein said header-type text contains at least one header parameter; (v) constructing a presumed document from a subset of the body text of said selected document, the constructed presumed document having (a) a header that includes one or more parameters from said header-type text located within said body text of said selected document, irrespective of whether the subject parameter of the header of said presumed document is the same as the subject parameter of the header of said selected document, and (b) body text that includes the text of said selected document located after said header-type text in said body text of said selected document, and associating said presumed document with a node; (vi) comparing a fingerprint of said presumed document to the previously stored fingerprint of at least one other document from among said plurality of original documents and in the case of a match between the fingerprints, merging a node associated with said presumed document with a node associated with a matching document having a fingerprint matching the fingerprint of said presumed document; and (vii) determining if the comparing of (vi) does not result in a match, processing repeatedly a remainder of the body text of said selected document for successive instances of header-type text according to step (iv), and for each successive instance of the header-type text, constructing a corresponding presumed document according to step (v), and comparing for any matching documents to the corresponding presumed document according to step (vi), said processing of steps (iv)-(vi) is repeatedly performed until a match is found in step (vi) or until no new instances of header-type text are found in step (iv), wherein each fingerprint comprises a representation of a corresponding document, and the plurality of nodes are arranged in terms of more than one tree, each tree comprising at least one node from the plurality of nodes, each tree comprising at least a root node and at least a leaf node, a root node being a node that is not a descendant of any other node, and a leaf node being a node that has no descendent nodes, a node not being prohibited from being both a root node and a leaf node, all nodes that are descendant from the root node are contained by the tree, each node being associated with either: (1) one of the original documents and any matching document thereof or (2) one of the presumed documents and any matching document thereof. 